System and method for automating the transfer of data from a web interface to a database or another web interface

ABSTRACT

Access information is received for a data sender interface accessible over a network and a data receiver interface accessible over the network. A set of navigation steps necessary to access data fields on the sender interface are determined. The data fields on the data sender interface are automatically mapped to data fields on the data receiver interface using at least one data mapping rule, such that a set of data field mappings is created. A data transfer scenario is generated using the set of navigation steps and the set of data field mappings, such that the data transfer scenario specifies a set of operations for transferring data from the sender interface to the receiver interface. The data transfer scenario is stored to computer readable media and can be executed any number of times to transfer data from the sending interface to the receiving interface.

The present application is a continuation-in-part of U.S. applicationSer. No. 11/856,586 filed on Sep. 17, 2007, which claims the benefit ofProvisional U.S. Patent Application Ser. No. 60/844,646, filed on Sep.15, 2006, the entire disclosures of which are hereby incorporated byreference in their entirety.

This application includes material which is subject to copyrightprotection. The copyright owner has no objection to the facsimilereproduction by anyone of the patent disclosure, as it appears in thePatent and Trademark Office files or records, but otherwise reserves allcopyright rights whatsoever.

FIELD OF THE INVENTION

The instant disclosure relates to the field of data transfer, and inparticular to a system and method for automating the transfer of datafrom a web interface to a database or another web interface.

BACKGROUND OF THE INVENTION

Widespread adoption of the Internet by the public and the business worldhas lead to increasing amounts of data and information being availableon-line. Several Internet-based methods for transmitting informationexist, but the method is typically chosen by the sender without inputfrom the receiver. While the Internet was in its infancy, e-mail was themost popular means for transmitting information, whereas today, webpages are increasingly more popular means for transmitting information.Web page delivery has become popular with senders due to itscross-platform compatibility, convenience, flexibility, and ease ofmanagement. Receivers can navigate web pages to retrieve information ordata using hyperlinks, buttons, arrows, or the like, which can lead toother web pages containing more information or data.

SUMMARY OF THE INVENTION

In one embodiment, is a method. Access information is received, using acomputing device, for a data sender interface accessible over a network.Access information is received, using the computing device, for a datareceiver interface accessible over the network. A set of navigationsteps necessary to access data fields on the sender interface aredetermined using the computing device. The data fields on the datasender interface are then automatically mapped, using the computingdevice, to data fields on the data receiver interface using at least onedata mapping rule, such that a set of data field mappings is created. Adata transfer scenario is generated, using a computing device, using theset of navigation steps and the set of data field mappings, such thatthe data transfer scenario specifies a set of operations fortransferring data from the sender interface to the receiver interface.The data transfer scenario is stored to computer readable media and canbe executed any number of times to transfer data from the sendinginterface to the receiving interface.

In one embodiment, the invention is a computing device comprising aprocessor memory and a storage medium for tangibly storing thereonprogram logic for execution by the processor. In one embodiment, theprogram logic comprises: receiving logic for receiving accessinformation for a data sender interface accessible over a network;receiving logic for receiving access information for a data receiverinterface accessible over the network; navigation logic for determininga set of navigation steps necessary to access data fields on the senderinterface; mapping logic for automatically mapping the data fields onthe data sender interface to data fields on the data receiver interfaceusing at least one data mapping rule, such that a set of data fieldmappings is created; generation logic for generating a data transferscenario using the set of navigation steps and the set of data fieldmappings, such that the data transfer scenario specifies a set ofoperations for transferring data from the sender interface to thereceiver interface; and storing logic for storing the data transferscenario to computer readable media. In one embodiment, the datatransfer scenario can be executed any number of times to transfer datafrom the sending interface to the receiving interface.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features, and advantages of theinvention will be apparent from the following more particulardescription of preferred embodiments as illustrated in the accompanyingdrawings, in which reference characters refer to the same partsthroughout the various views. The drawings are not necessarily to scale,emphasis instead being placed upon illustrating principles of theinvention.

FIG. 1 illustrates some embodiments of a system architecture forautomating the transfer of data from a web interface to another.

FIG. 2 illustrates one embodiment of a process for automating thetransfer of data from a data sender interface to a database to a datareceiver interface.

FIG. 3A and 3B illustrate one embodiment of set of rules for mappingdata files comprising a thesaurus.

FIG. 4 illustrates one embodiment of a mapping report displaying fieldmapping for multiple receiving data fields for multiple sendingwebsites.

DETAILED DESCRIPTION

The present invention is described below with reference to blockdiagrams and operational illustrations of methods and devices to selectand present media related to a specific topic. It is understood thateach block of the block diagrams or operational illustrations, andcombinations of blocks in the block diagrams or operationalillustrations, can be implemented by means of analog or digital hardwareand computer program instructions.

These computer program instructions can be provided to a processor of ageneral purpose computer, special purpose computer, ASIC, or otherprogrammable data processing apparatus, such that the instructions,which execute via the processor of the computer or other programmabledata processing apparatus, implements the functions/acts specified inthe block diagrams or operational block or blocks.

In some alternate implementations, the functions/acts noted in theblocks can occur out of the order noted in the operationalillustrations. For example, two blocks shown in succession can in factbe executed substantially concurrently or the blocks can sometimes beexecuted in the reverse order, depending upon the functionality/actsinvolved.

For the purposes of this disclosure the term “server” should beunderstood to refer to a service point which provides processing,database, and communication facilities. By way of example, and notlimitation, the term “server” can refer to a single, physical processorwith associated communications and data storage and database facilities,or it can refer to a networked or clustered complex of processors andassociated network and storage devices, as well as operating softwareand one or more database systems and applications software which supportthe services provided by the server.

For the purposes of this disclosure a computer readable medium storescomputer data, which data can include computer program code that isexecutable by a computer, in machine readable form. By way of example,and not limitation, a computer readable medium may comprise computerreadable storage media, for tangible or fixed storage of data, orcommunication media for transient interpretation of code-containingsignals. Computer readable storage media, as used herein, refers tophysical or tangible storage (as opposed to signals) and includeswithout limitation volatile and non-volatile, removable andnon-removable media implemented in any method or technology for thetangible storage of information such as computer-readable instructions,data structures, program modules or other data. Computer readablestorage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM,flash memory or other solid state memory technology, CD-ROM, DVD, orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other physical ormaterial medium which can be used to tangibly store the desiredinformation or data or instructions and which can be accessed by acomputer or processor.

Reference will now be made in detail to embodiments of the disclosedsystem and method for automating the transfer of data from a webinterface to a database or another web interface, examples of which areillustrated in the accompanying drawings.

The parent application of this application, U.S. application Ser. No.11/856,586, describes systems and methods for automating the transfer ofdata from a web interface to another web interface. In some embodiments,the system described in the Ser. No. 11/856,586 application, provides ascenario designer that enables a user to interactively map fields on asending web interface to fields on a receiving web interface andgenerate a data transfer scenario for transferring data from the sendinginterface to the receiving interface. In some embodiments, the Ser. No.11/856,586 application additionally provides a scenario executor thattransfers data from sending web interfaces to receiving web interfacesusing data transfer scenarios generated by the scenario designer.

In some embodiments, this application describes an automated scenariogeneration process that can substantially eliminate the need for, interalia, interactively mapping a sending interface to a receiving interfaceusing a scenario designer user interface. In some embodiments, theautomated scenario generation process can use network addresses ofsending and receiving interfaces and a set of data mapping rules togenerate a data transfer scenario that can be used by a scenarioexecutor to transfer data from the sending interface to the receivinginterface.

In some embodiments, an automated scenario generation process could besupported by a set of one or more additional functions provided by thescenario designer of the Ser. No. 11/856,586 application, which could beaccessed through the scenario designer's user interface. Alternatively,an automated scenario designer could be a stand-alone system thatgenerates data transfer scenarios for input into a scenario executor orother automated data transfer processes. In some embodiments, datatransfer scenarios generated by an automated scenario generator could beinput to the scenario designer of the 11/856,586 for revision andfinalization.

FIG. 1 illustrates some embodiments of a system architecture 100 forautomating the transfer of data from a web interface to another. Data ishoused on at least one sender web interface 110. The sender webinterface 110 is communicatively coupled with a server 120 via a privateor non-private network, such as, for example, the Internet. The server120 can also be communicatively coupled with a receiver web interface130 or a database 140.

In some embodiments, a data transfer application, or scenario executor,running on server 120, automates the transfer of data between sender webinterface 110 and receiver web interface 130 and/or database 140 byperforming one or more user-defined scripts. In some embodiments, dataon sender interfaces, receiver interfaces, and databases are grouped inrows that belong to entities. Each entity owns a row of data fields,which are its attributes. In some embodiments, transfer of data isperformed one row at a time. When there is a change in any of the datafields for any row, that field is transferred to the receiver databaseor web interface for update in that entity's record.

In some embodiments, the server 120 is also be communicatively coupledwith one or more data mapping rules database 150 that can be used by anautomated scenario generator to map sender web interface 110 data fieldsto receiver web interface fields 130 or database fields 140 andautomatically generate data transfer scenarios.

The automated scenario generator and data transfer applications cancomprise one or more forms, executable on a networked computing device,such as, but not limited to, compiled, stand-alone machine code, such asthat written in Visual C++, Visual Basic, Delphi, or the like; run-timescripts, such as those written in JavaScript, Visual Basic Script, orthe like; macros, command level files, or the like.

An automated data transfer system could be used to transfer any type ofdata from one interface to another. For example, a user may want tostore hourly weather readings for his locale in database 140. Sender webinterface 110 may comprise a weather website requiring the user toprovide login credentials prior to providing weather readings. The datatransfer application can automatically provide the login credentials tosender web interface 110 on an hourly basis, retrieve the weatherreadings, and store them in database 140, without requiring anyinteraction by the user.

By way of another example, without limitation, a tax advisor may wish toautomatically send state lottery winners promotional materials regardingservices offered by the tax advisor. In this example, sender webinterfaces 110 could comprise a state lottery website displaying thelottery winners' names and hometown as well as a phone directorywebsite, for locating the lottery winners' home address. Receiver webinterface 130 would comprise a printing website that the tax advisoruses to print promotional materials. The data transfer application canperiodically query the state lottery website to retrieve the name(s) ofnew lottery winners. After receiving the name of a new lottery winner,the data transfer application would query the phone directory website toretrieve the lottery winner's home address. The data transferapplication would then provide any necessary credentials, input thelottery winner's name and address into the printing website, and placean order to have promotional materials sent to the lottery winner. Inboth of the preceding examples, system architecture 100 and the scriptsrun by the data transfer application allow the user to transfer databetween web interfaces and databases, while alleviating the burdenstypically associated with doing so.

FIG. 2 illustrates a process for automating the transfer of data from adata sender interface to a database to a data receiver interface. Accessinformation is received 210, using a computing device, for a datainterface accessible over a network. Access information is received 220,using a computing device, for a data receiver interface accessible overa network. Navigation steps necessary to access information via thesender interface are determined 230 using a computing device. Fields onthe data sender interface are then mapped, using the computing device,to fields on the data receiver interface 240. The navigation steps andthe data field mappings are used to generate 250 a data transferscenario. The data transfer scenario is stored 260 on a database orother computer-readable storage media. The data transfer scenario canthen be executed 270 one to many times to transfer data from the senderinterface to the receiver interface. These operations will now bediscussed in detail.

In block 210 of FIG. 2, access information is received, using acomputing device, for a data sender interface accessible over a network.In some embodiments, the data sender interface is a web site and theaccess information comprises a URL. In some embodiments, accessinformation for the data sender interface additionally includes logincredentials. In some embodiments, the network is the Internet and theweb site is accessible over the Internet using the URL. In someembodiments, the network is a private network, for example, an intranet,and the data sender interface is a webpage accessible over the network.

In some embodiments, the data sender access information is received froma user, over a network, via a user interface. In some embodiments, theuser interface provides elements to allow the entry of URL, for anetwork accessible sender interface. In some embodiments, the userinterface additionally provides elements to allow the entry of logincredentials for access to the data sender interface. In someembodiments, the user interface is provided by a scenario designerapplication such as is disclosed in U.S. application Ser. No.11/856,586. In other embodiments, data sender interface accessinformation could be provided via automated means, such as, for example,a batch script or an automated process that identifies potential datasources on the Internet (e.g. via a web search).

In block 220 of FIG. 2, access information is received, using acomputing device, for a data receiver interface accessible over anetwork. In some embodiments, the data receiver interface is a web siteand the access information comprises a URL. In some embodiments, accessinformation for the data sender interface additionally includes logincredentials. In some embodiments, the network is the Internet and theweb site is accessible over the Internet using the URL. In someembodiments, the network is a private network, for example, an intranet,and the data sender interface is a webpage accessible over the network.In some embodiments, the data receiver interface is an interface forupdating a database.

In some embodiments, the data receiver access information is receivedfrom a user, over a network, via a user interface. In some embodiments,the user interface provides elements to allow the entry of URL, for anetwork accessible receiver interface. In some embodiments, the userinterface additionally provides elements to allow the entry of logincredentials for access to the data receiver interface. In someembodiments, the user interface is provided by a scenario designerapplication such as is disclosed in U.S. application Ser. No.11/856,586. In other embodiments, data receiver interface accessinformation could be provided via automated means, such as, for example,a batch script or as a default option stored in a profile.

In block 230 of FIG. 2, navigation steps necessary to access informationvia the sender interface are then determined 230 using a computingdevice. In the case where a data sender interface is a website,information of interest may be located on multiple web pages thatnormally require one or more user interface actions to access the data.In one example, a website may initially display data using a summarylist comprising a number of lines, where each line relates to adifferent person or business (e.g. a directory). More detailedinformation regarding the person or business may only be accessible byselecting a one of the lines on the list. In another example,information of interest may be displayed on multiple pages wherenavigation from page to page occurs by, for example, through a “Next”control.

A data transfer scenario needs sufficient information to navigate tointerface elements that contain data of interest. This information maybe gathered in a number of ways, some of which may be fully automated,and some of which may require more or less manual intervention on thepart of a user. In some embodiments, data access information for thesender interface may point directly to an interface element, forexample, a webpage, that contains all of the data of interest providedby the interface. In such case, no additional navigation information isrequired.

Commonly, however, websites are composed of multiple pages, and data ofinterest are located on multiple pages. In some embodiments, navigationinformation could be gathered by an automated process that maps all ofthe pages accessible through the website and identifies interfaceactions or links necessary to proceed from one page to another. In someembodiments, such functionality could be provided by a scenario designeroperating in a batch mode. In another embodiment, the scenario designerrequires control by a user.

In some embodiments, data interface navigation information could becollected by a scenario designer by monitoring user interaction with thesender web interface, such as is disclosed in U.S. application Ser. No.11/856,586. In other embodiments, data navigation information could begathered initially via an automated process. In another embodiment,automatically gathered information can be edited via a scenario designeruser interface such as is disclosed in U.S. application Ser. No.11/856,586. In one embodiment, data navigation information is stored ona database in association with an identification of an interface towhich it relates.

In block 240 of FIG. 2, fields on the data sender interface are thenautomatically mapped, using the computing device, to fields on the datareceiver interface. In some embodiments, the automated process uses arule set to automatically map data values from the sender web interfaceto a data receiver interface or user defined variables without the needfor user interaction. In some embodiments, data navigation steps for theinterface are used by the mapping process to navigate from one elementof the sender interface to the next for the purpose of mapping elementson each interface element (e.g. navigating through all the pages of awebsite and mapping fields on each page).

In some embodiments, the rule set is expressed as a thesaurus 300, suchas that illustrated in FIG. 3. The thesaurus comprises one or moreentries, each entry comprising a receiving data field 310 and one ormore sending data fields 320. The receiving data fields 310 define datafields needed by a receiving website or a receiving database. Thesending data fields 320 define data fields on sending websites that maycorrespond to the receiving data fields 310 i.e. are synonyms for thesending data fields. The thesaurus may be created using any techniqueknown in the art, for example, using a spreadsheet.

In some embodiments, for each sending data interface, the elements ofthe sending interface (e.g. pages on a website) are searched for sendingdata fields 320, so literally, or identified by the thesaurus. Where asending data field 320 is found on a sending interface, it is mapped tothe corresponding receiving data field for that sending interface and adata mapping rule is created. Each data mapping rule comprises anidentification of one of the at least one data inputs on the receiverdatabase or receiver web interface and at least one identification ofone of the data fields on the sender web interface For example assumethe field “Assigned To” (see FIG. 3, row 1) is found on some websiteXYZ. That field is mapped to the receiving field “Contact”

In some embodiments, automated data mapping could be performed withoutuser interaction. In some embodiments, automated data mapping could beperformed then be presented to the user for review, modification andapproval using a scenario designer user interface such as is disclosedin U.S. application Ser. No. 11/856,586 for review, modification andapproval. In one embodiment, data field mapping is stored on a databasein association with an identification of an interface to which itrelates.

In some embodiments, data mapping reporting functions can additionallybe provided. FIG. 4 illustrates some embodiments of a mapping report400. The report 410 displays field mapping for multiple receiving datafields 410 for multiple sending websites 420.

In block 250 of FIG. 2, navigation steps and data field mappings for asender interface and a receiver data interface are then used to generatea data transfer scenario. In one embodiment, the data transfer scenariocomprises sufficient information for an automated process to obtain datafrom the sender interface and transfer the information to the receiverinterface. In one embodiment, such information can include data fieldmappings and control logic for navigating the sender interface andextracting information from interface elements. In some embodiments,such control logic can perform loop processing of data stored on asender interface in a table, grid, or other similar format.

In some embodiments, data transfer scenario generation could beperformed without user interaction. In some embodiments, data transferscenario generation could be performed then be presented to the user forreview, modification and approval using a scenario designer userinterface such as is disclosed in U.S. application Ser. No. 11/856,586for review, modification and approval.

In block 260 of FIG. 2, The data transfer scenario is stored 260 on adatabase or other computer readable media. In some embodiments, datatransfer scenario generation and data transfer scenario execution areseparate processes whose only relation to one another is through datatransfer scenarios. In some embodiment, data transfer scenarios aregenerated for later use by one or more automated data transferprocesses, such as, for example, a scenario executor.

In various embodiments, data transfer scenarios can take a number ofdifferent forms. In some embodiments, data transfer scenario generationcompiles executable software which can be run by, for example, server120 of FIG. 1 or other such device. In some embodiments, data transferscenario generation creates scenarios comprising macros and routineswhich are executed by an automated data transfer application installedon a server such as, for example, server 120 of FIG. 1 or other suchdevice. In one embodiment, data transfer scenarios are expressed as XMLcode that is capable of being executed an automated data transferapplication. Appendices A through F of U.S. application Ser. No.11/856,586 illustrate a number of exemplary XML based data transferscenarios.

FIG. 5 is a block diagram illustrating an internal architecture of anexample of a computing device, such server 120 of FIG. 1, in accordancewith one or more embodiments of the present disclosure. A computingdevice as referred to herein refers to any device with a processorcapable of executing logic or coded instructions, and could be a server,personal computer, set top box, smart phone, pad computer or mediadevice, to name a few such devices. As shown in the example of FIG. 5,internal architecture 510 includes one or more processing units (alsoreferred to herein as CPUs) 512, which interface with at least onecomputer bus 502. Also interfacing with computer bus 502 are persistentstorage medium/media 506, network interface 514, memory 504, e.g.,random access memory (RAM), run-time transient memory, read only memory(ROM), etc., media disk drive interface 508 as an interface for a drivethat can read and/or write to media including removable media such asfloppy, CD-ROM, DVD, etc. media, display interface 510 as interface fora monitor or other display device, keyboard interface 516 as interfacefor a keyboard, pointing device interface 518 as an interface for amouse or other pointing device, and miscellaneous other interfaces notshown individually, such as parallel and serial port interfaces, auniversal serial bus (USB) interface, and the like.

Memory 504 interfaces with computer bus 502 so as to provide informationstored in memory 504 to CPU 512 during execution of software programssuch as an operating system, application programs, device drivers, andsoftware modules that comprise program code, and/or computer-executableprocess steps, incorporating functionality described herein, e.g., oneor more of process flows described herein. CPU 512 first loadscomputer-executable process steps from storage, e.g., memory 504,storage medium/media 506, removable media drive, and/or other storagedevice. CPU 512 can then execute the stored process steps in order toexecute the loaded computer-executable process steps. Stored data, e.g.,data stored by a storage device, can be accessed by CPU 512 during theexecution of computer-executable process steps.

Persistent storage medium/media 506 is a computer readable storagemedium(s) that can be used to store software and data, e.g., anoperating system and one or more application programs. Persistentstorage medium/media 506 can also be used to store device drivers, suchas one or more of a digital camera driver, monitor driver, printerdriver, scanner driver, or other device drivers, web pages, contentfiles, playlists and other files. Persistent storage medium/media 506can further include program modules and data files used to implement oneor more embodiments of the present disclosure.

Those skilled in the art will recognize that the methods and systems ofthe present disclosure may be implemented in many manners and as suchare not to be limited by the foregoing exemplary embodiments andexamples. In other words, functional elements being performed by singleor multiple components, in various combinations of hardware and softwareor firmware, and individual functions, may be distributed among softwareapplications at either the client level or server level or both. In thisregard, any number of the features of the different embodimentsdescribed herein may be combined into single or multiple embodiments,and alternate embodiments having fewer than, or more than, all of thefeatures described herein are possible. Functionality may also be, inwhole or in part, distributed among multiple components, in manners nowknown or to become known. Thus, myriad software/hardware/firmwarecombinations are possible in achieving the functions, features,interfaces and preferences described herein. Moreover, the scope of thepresent disclosure covers conventionally known manners for carrying outthe described features and functions and interfaces, as well as thosevariations and modifications that may be made to the hardware orsoftware or firmware components described herein as would be understoodby those skilled in the art now and hereafter.

Furthermore, the embodiments of methods presented and described asflowcharts in this disclosure are provided by way of example in order toprovide a more complete understanding of the technology. The disclosedmethods are not limited to the operations and logical flow presentedherein. Alternative embodiments are contemplated in which the order ofthe various operations is altered and in which sub-operations describedas being part of a larger operation are performed independently.

While various embodiments have been described for purposes of thisdisclosure, such embodiments should not be deemed to limit the teachingof this disclosure to those embodiments. Various changes andmodifications may be made to the elements and operations described aboveto obtain a result that remains within the scope of the systems andprocesses described in this disclosure.

1. A method comprising: receiving access information, using a computingdevice, for a data sender interface accessible over a first network;receiving access information, using the computing device, for a datareceiver interface accessible over a second network, wherein said secondnetwork is the same as or different from said first network;determining, using the computing device, a set of navigation stepsnecessary to access data fields on the sender interface; automaticallymapping, using the computing device, the data fields on the data senderinterface to data fields on the data receiver interface using at leastone data mapping rule, such that a set of data field mappings iscreated; generating, using a computing device, a data transfer scenariousing the set of navigation steps and the set of data field mappings,such that the data transfer scenario specifies a set of operations fortransferring data from the sender interface to the receiver interface;and storing, using the computing device, the data transfer scenario tocomputer readable media.
 2. The method of claim 1, such that the atleast one data mapping rule comprises a thesaurus comprising one or moreentries, each entry comprising a receiving data field and one or moresending data fields.
 3. The method of claim 1, such that the data senderinterface is a website, and determining a set of navigation stepscomprises automatically identifying web pages accessible through thewebsite and identifying interface actions necessary to navigate betweenthe web pages.
 4. The method of claim 1, such that the data senderinterface is a website, and determining a set of navigation stepscomprises monitoring user interaction with the website.
 5. The method ofclaim 1, such that the access information for a data sender interfacecomprises a URL for a page on a website.
 6. The method of claim 5, suchthat the access information for a data sender interface additionallycomprises login credentials.
 7. The method of claim 1, such that theaccess information for a data receiver interface comprises a URL for apage on a website.
 8. The method of claim 1, such that the accessinformation for a data receiver interface comprises a network addressfor an interface for updating a database.
 9. The method of claim 1comprising: executing, using the computing device, the data transferscenario, such that data is transferred from the sender interface to thereceiver interface in accordance with the data transfer scenario. 10.The method of claim 1, such that the data transfer scenario is executedautomatically on a predetermined schedule.
 11. The method of claim 1,such that the data transfer scenario is executed on-demand.
 12. Acomputing device comprising: a processor memory; a storage medium fortangibly storing thereon program logic for execution by the processor,the program logic comprising: receiving logic for receiving accessinformation for a data sender interface accessible over a first network;receiving logic for receiving access information for a data receiverinterface accessible over a second network, wherein said second networkis the same as or different from said first network; navigation logicfor determining a set of navigation steps necessary to access datafields on the sender interface; mapping logic for automatically mappingthe data fields on the data sender interface to data fields on the datareceiver interface using at least one data mapping rule, such that a setof data field mappings is created; generation logic for generating adata transfer scenario using the set of navigation steps and the set ofdata field mappings, such that the data transfer scenario specifies aset of operations for transferring data from the sender interface to thereceiver interface; and storing logic for storing the data transferscenario to computer readable media.
 13. The computing device of claim12, such that the at least one data mapping rule comprises a thesauruscomprising one or more entries, each entry comprising a receiving datafield and one or more sending data fields.
 14. The computing device ofclaim 12, such that the data sender interface is a website, and thenavigation logic determines the set of navigation steps by automaticallyidentifying web pages accessible through the website and identifiesinterface actions necessary to navigate between the web pages.
 15. Thecomputing device of claim 12, such that the data sender interface is awebsite, and the navigation logic determines the set of navigation stepsby monitoring user interaction with the website.
 16. A computer-readablestorage medium for tangibly storing thereon computer readableinstructions for a method comprising: receiving access information for adata sender interface accessible over a first network; receiving accessinformation for a data receiver interface accessible over a secondnetwork, wherein said second network is the same as or different fromsaid first network; determining a set of navigation steps necessary toaccess data fields on the sender interface; automatically mapping thedata fields on the data sender interface to data fields on the datareceiver interface using at least one data mapping rule, such that a setof data field mappings is created; generating a data transfer scenariousing the set of navigation steps and the set of data field mappings,such that the data transfer scenario specifies a set of operations fortransferring data from the sender interface to the receiver interface;and storing the data transfer scenario to a second computer readablemedia.
 17. The computer-readable storage medium of claim 16, such thatthe at least one data mapping rule comprises a thesaurus comprising oneor more entries, each entry comprising a receiving data field and one ormore sending data fields.
 18. The computer-readable storage medium ofclaim 16, such that the data sender interface is a website, anddetermining a set of navigation steps comprises automaticallyidentifying web pages accessible through the website and identifyinginterface actions necessary to navigate between the web pages.
 19. Amethod comprising: receiving access information, using a computingdevice, for a data sender interface accessible over a first network;receiving access information, using the computing device, for a databaseaccessible over a second network, wherein said second network is thesame as or different from said first network; determining, using thecomputing device, a set of navigation steps necessary to access datafields on the sender interface; automatically mapping, using thecomputing device, the data fields on the data sender interface to datafields in the database using at least one data mapping rule, such that aset of data field mappings is created; generating, using a computingdevice, a data transfer scenario using the set of navigation steps andthe set of data field mappings, such that the data transfer scenariospecifies a set of operations for transferring data from the senderinterface to the database; and storing, using the computing device, thedata transfer scenario to computer readable media.
 20. The method ofclaim 19, such that the at least one data mapping rule comprises athesaurus comprising one or more entries, each entry comprising areceiving data field and one or more sending data fields.
 21. The methodof claim 19, such that the data sender interface is a website, anddetermining a set of navigation steps comprises automaticallyidentifying web pages accessible through the website and identifyinginterface actions necessary to navigate between the web pages.
 22. Themethod of claim 19, such that the data sender interface is a website,and determining a set of navigation steps comprises monitoring userinteraction with the website.
 23. The method of claim 19, such that theaccess information for a data sender interface comprises a URL for apage on a website.
 24. The method of claim 19, such that the accessinformation for a data sender interface additionally comprises logincredentials.
 25. The method of claim 19 comprising: executing, using thecomputing device, the data transfer scenario, such that data istransferred from the sender interface to the database in accordance withthe data transfer scenario.
 26. The method of claim 19, such that thedata transfer scenario is executed automatically on a predeterminedschedule.
 27. The method of claim 19, such that the data transferscenario is executed on-demand.
 28. A computing device comprising: aprocessor memory; a storage medium for tangibly storing thereon programlogic for execution by the processor, the program logic comprising:receiving logic for receiving access information for a data senderinterface accessible over a first network; receiving logic for receivingaccess information for a database accessible over a second network,wherein said second network is the same as or different from said firstnetwork; navigation logic for determining a set of navigation stepsnecessary to access data fields on the sender interface; mapping logicfor automatically mapping the data fields on the data sender interfaceto data fields in the database using at least one data mapping rule,such that a set of data field mappings is created; generation logic forgenerating a data transfer scenario using the set of navigation stepsand the set of data field mappings, such that the data transfer scenariospecifies a set of operations for transferring data from the senderinterface to the database; and storing logic for storing the datatransfer scenario to computer readable media.
 29. The computing deviceof claim 28, such that the at least one data mapping rule comprises athesaurus comprising one or more entries, each entry comprising areceiving data field and one or more sending data fields.
 30. Thecomputing device of claim 28, such that the data sender interface is awebsite, and the navigation logic determines the set of navigation stepsby automatically identifying web pages accessible through the websiteand identifies interface actions necessary to navigate between the webpages.
 31. The computing device of claim 28, such that the data senderinterface is a website, and the navigation logic determines the set ofnavigation steps by monitoring user interaction with the website.
 32. Acomputer-readable storage medium for tangibly storing thereon computerreadable instructions for a method comprising: receiving accessinformation for a data sender interface accessible over a first network;receiving access information for a database accessible over a secondnetwork, wherein said second network is the same as or different fromsaid first network; determining a set of navigation steps necessary toaccess data fields on the sender interface; automatically mapping thedata fields on the data sender interface to data fields on the databaseusing at least one data mapping rule, such that a set of data fieldmappings is created; generating a data transfer scenario using the setof navigation steps and the set of data field mappings, such that thedata transfer scenario specifies a set of operations for transferringdata from the sender interface to the database; and storing the datatransfer scenario to a second computer readable media.
 33. Thecomputer-readable storage medium of claim 32, such that the at least onedata mapping rule comprises a thesaurus comprising one or more entries,each entry comprising a receiving data field and one or more sendingdata fields.
 34. The computer-readable storage medium of claim 32, suchthat the data sender interface is a website, and determining a set ofnavigation steps comprises automatically identifying web pagesaccessible through the website and identifying interface actionsnecessary to navigate between the web pages.